home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
rbbs_pc
/
jdrbbs08.zip
/
DOCS_ETC.ZIP
/
NOT_DOCS.DOC
< prev
next >
Wrap
Text File
|
1993-04-05
|
129KB
|
2,267 lines
NOT DOCS
CONTENTS Line Topic
──── ───────────────────────────────────────────────────────
81 INTRODUCTION
89 LICENSE
198 BUGS
255 HASSLES
263 ALTERNATIVES
272 Command stacking
281 Various modes of expertise
290 Page lengths
298 Mixing private and public messages
314 Editing lines of a message
324 Multi-line file descriptions
330 Non-ANSI support
343 Archivers
355 <Ctrl>Q, <Ctrl>S, <Ctrl>C
363 No message numbers or constantly renumbered numbers
371 The authors real name message field
380 Generating a password for the new user
394 Threaded messages
417 Wildcards
442 File point system
448 Colors
460 User capture to file
465 Script Languages
475 Misc.
483 COMPETITION
485 Auntie
663 Spitfire
725 Minihost
743 RyBBS
790 IronHenge
1039 TurboBBS
1052 Searchlight BBS
1122 OmegaBBS
1168 Radioactive Telegard BBS
1247 WWIV
1291 WILDCAT!
1324 Professional OLEcom
1337 UltraBBS
1363 RBBS-PC
1383 Telegard
1440 Forum-PC
1489 ViSiON
1524 ICP
1528 Socrates BBS System
1555 T.A.G.
1594 FeatherNet
1603 QuickBBS
1625 Virtual BBS/NET
1659 RemoteAccess
1703 MSYS
1717 OPUS
1726 X-ZotIks
1731 FORCE! BBS
1740 PICS
1750 ROS
1756 Common Ground
1765 COLLIE
1779 Minotaur
1785 Major BBS
1809 Falken
1842 Osiris
1948 Maximus-CBCS
1970 SuperBBS
1982 Renegade
1985 Sapphire
2025 Mach-10
2044 MIST+
2051 The Silver Bullet
2066 Celerity
2112 HERITAGE NOTES
2174 HISTORY
INTRODUCTION These are "not docs". They describe things the software does
not yet do, things I have no plans to get it to do, and
things you cannot (yet) do with it.
It also details the agreement under which you use this
software.
LICENSE It seems I am granting you a limited license to utilize this
software. The program is copyrighted after all.
So in that spirit, here are the "rules" you must follow:
No more than 5% of the code (in bytes) may be used for
your commercial/shareware/freeware products.
For each subroutine you do use for your
commercial/shareware products, I would like to see a
royalty of one cent (per subroutine) for each copy of
your program that you sell.
No utility utilizing the data structures, files created
by, or files of this software may charge a higher fee
(shareware or otherwise) than the registration fee I
charge.
Further, programs that use more than 5% of the code, or
make use of the software's data structures may, at any
time, be fully incorporated into future releases of this
software without compensation or acknowledgement on my
part.
I GRANT NO RIGHT FOR ANY DISK SERVICE OR ANYBODY TO
CHARGE ANY FEE FOR THIS PRODUCT. THIS INCLUDES ANY
COSTS, INCLUDING POSTAGE AND HANDLING, THAT CAN BE
IMAGINED. So, as long you distribute this product for
free, I have no problems. It is allowed to be posted on
on general payment BBS's, but may not be packaged with
other software as part of a package purchase. You may
not rent or lease it to others. CD-ROM services may
include it on their ROM's. Shareware catalogs may
include it in their catalog.
Ok, lets get down and dirty: what I want to see is 3rd party
software also include their source, and preferably be tested
by me first--so I may optionally choose to include it in the
next version (you always get credit for your work). If you
go off and write a log analyzer (say) and charge a $50 fee
for it, I reserve the right to, and probably will, include it
in my source. However, since you may be unhelpful in said
regard--I will most likely write a better one that utilizes
many of your ideas and put it in the program. Why all this?
It is mainly to keep quality control over the product, this
includes keeping it up-to-date with the best possible
routines and options. Any 3rd party software that pops up
means I forgot something, or there is a better way to do it
than I have done it. And all these silly rules will allow me
to do it like the 3rd party guy did. Also, if you are using
the code for commercial products then you (really) should
develop it yourself--it is hard to maintain someone elses
code. And this code will change often.
The way around these restrictions: utilize my data
structures/etc. as part of a general system (where you are
making use of the data from many BBS programs or other). Even
then I may "peel off" from your product your ideas, but at
least I would not be absorbing your whole product. I want
free and open software, 3rd party developers should only
develop routines that can be added onto the source, and then
released as part of the next version of this BBS software as
a whole. The "proper" 3rd party product: 1. design a
subroutine to work with this source, 2. send it up to my BBS,
3. I will confirm what it does, make sure it is compatible,
and perhaps optimize it, 4. it will then be included as part
of the source. If there is a capability/problem that a 3rd
party developer sees, I will see it as well, and work to
add/fix it. I really do not want to see a hundred files
"related" to JDR_BBS--whether code fragments or fully
functional sub-programs. If you want to write, say, a log
analyzer program without running it by me first, you can BET
that the next release will have a log analyzer written by me-
-totally wasting your effort, and forcing me to re-invent
your wheel.
Perhaps the one thing that would really make me mad: if you
were to take this software, and use most of it for your own
BBS program. It does not matter what language you convert it
into. You can reverse engineer it--like AMI/AWARD/etc. does
with BIOS, or AMD does with INTEL chips. But like both of
these examples, just because the specs are public domain,
does not mean you can make duplicates. You can modify this
software for your own use, but you cannot modify (or reverse
engineer) this software and then re-distribute it (in any
form). This has occurred with so many other BBS programs
that it makes me mad that nobody out there seems to care.
Example: you just bought an Amiga, and decide to make your
BBS Amiga specific using the Amiga computer. Having run
JDR_BBS for 10 years, you like it. So you make some
modifications to get it to work properly on the Amiga. Fine.
Then you get interest from other Amiga sysops. So you give
them copies, or create a JDR_BBS-FORTHEAMIGA file and post
it. Wrong. You should dump your modifications on me, then I
will include them in the next release, with a configuration
question: "IBM or Amiga?". You will get credit for your
modifications, everyone gets an Amiga version, and we are all
happy.
This is my little baby. I will do what is necessary to make
sure it is protected and grows. I probably will not sue an
individual--but I am not beneath ridiculing you in public.
(Jeez, it is no wonder more source code is not around...one
has to do a lot just to protect themselves from others using
the source against them.)
BUGS It is probably due to some conflict in my log file names.
But whenever BiModem is run, it leaves a 2048 byte file that
is found only with CHKDSK. Think it is because I have DSZ
and BiModem both using DSZLOG for their output and this must
be causing a conflict. It is minor and I will look into it
later.
Support for time distinctions and circular buffers in message
areas are not yet supported. As well as a variety of other
stuff one sees in BBS-VAR.BAS.
When deleting files externally--using the DOS DEL command,
and restarting the BBS, any reviews that a deleted file had,
will still be there. You will need to delete them by hand
with Remove A Line.
When LINKing, it will want the run-time library. It seems to
be a bug with Basic PDS. Just ignore it.
When using <alt>d to call another BBS: if there is no
connection, and no BUSY--eg. just RINGING, and you hit
[Enter]--the software did not hang up--you should do an
H0<ret> to hang up the phone.
I have noticed a bug in TeleMate 3.02's wrap-around routine:
"────┐│". When the "┐" is at column 80, instead of
immediately wrapping and using the "│", it instead
processes the "" while it is still on that same line. I
do not know if this is true of other ansi codes (for color
codes it does not cause troubles doing it this way). For
color codes, and some other ansi codes, this may be the best
method for changing colors (since a wrap causes a new line
25)--but a check for "" is needed.
Along similar lines, there is another bug in TeleMate 3.02
when it is used in Avatar mode. This is most clearly seen
with my various menu ansi's--as it chops the upper right
corner off. The reason seems to be the same as above, except
it only happens in Avatar mode. When at column 80 (that is,
I had outputted 80 characters on the line--so it's not really
column 80), I change colors with "
" in ansi (not
Avatar), and it seems to delete the character at column 80,
and start the next character (which would normally wrap to
the first position on the next line) at that column 80
position. The Avatar codes I send add up to 80, so I suspect
it's TeleMate.
I have also been told that some programs do not properly
control "" (clear to end-of-line) within a window. For
example, if a comm program is in 132 column mode, and you
have an 80 column window to which you have contacted a BBS.
The software, upon encountering a "" will clear past the
window. I have been told it appears when entering messages.
The only solution is for the authors of that users program to
fix this "end-of-line bleeding" problem.
HASSLES When adding a new file by copying it into a file area, you
must first do a "list file area contents" (or a restart of
the BBS from a full exit) before the system "sees" it for you
to modify with File Maintenance.
The screen does not redraw after shell to dos.
ALTERNATIVES Things this software does not specifically support, with work-
around's or alternatives.
When I say I will never add/support it, I mean I will never
program it. If someone does it, I will gladly include their
routine into future BBS versions. I will not lock out any
routines--it is just that there are some I do not think worth
my time and effort.
Command For example, r;n For [R]ead and then [N]ew. The menus, and
stacking most of the commands are hot-key'd or auto-sensed. So no
speed advantage occurs using stacks. The most used "stack",
logging in (name;password) could be supported with a simple
alteration (IF INSTR(input$,";") > 0 THEN...). But then one
risks screwing up their auto-sensed name. Further, any
routines/questions that could be improved by "stacking" could
be programmed to do so at that location.
Various modes For example; beginner, novice, expert. The menus are hot-
of expertise key'd, so this is not needed. Experts can type faster than
the menu appears, or wait for it to be drawn. This includes
"info" before doing something (such as L&D or BBS Review)--
just make sure the text you output is set to handle the
appropriate keys (making it hot-text). The only flaw in this
logic is when the input is numbers, then experts and novices
alike must wait for whatever pre-text is completely sent.
Page lengths The space bar pauses text that (you the sysop decide) is
going to be long, eliminating the need for page length
handling. Only when a user is using, say, an 8 line screen
and wishes to pause every 7 lines will problems arise. This
software requires full ANSI capabilities to use, so that
particular user will have many problems, not just with long
messages or text files.
Mixing private I do not support this. It implies that the message area is
and public more important than the type of message (send a private
messages message about cars only in the "cars" message area--not the
private area?). If a message is so personal that it needs to
be private, it should be sent in the private mail area.
Sure, the subject may belong in one of message areas, but
then, all messages could be grouped into a "general messages"
topic area as well. Modifying this software for mixed public
and private (or access by security levels--different levels
for each message) would be very difficult. Very difficult to
change this software to mix message types. As the access and
type for the messages is not determined by the messages, but
by the area they are in--a fundamental design consideration.
A private message moved to a public area becomes public, and
vice-versa.
Editing lines Could be implemented. Just ask for the line number, display
of a message that lines contents in brown and let the user overwrite it.
Perhaps using cursor movement keys as well. Then just
"replace" (delete old string for that line and merge in the
new string at the old string's start position). I opted for
the simple search and replace of a single occurrence because
that is all that is usually needed. More complex editing can
be done with the Insert and Delete options. My
implementation also requires much less instructions.
Multi-line This is essentially accomplished by "reviewing" the file. A
file minor pain in that the user cannot enter a whole long
descriptions description at once, but the vast majority of descriptions
are not multi-line (and many that are contain no additional
information).
Non-ANSI I do not. Even though it may be wanted for such things as
support faster screen writes and Unix users. We are heading for
graphic BBS's, old out-dated techniques should be dropped
where appropriate. But if you really want ASCII-only text,
filter the ANSI codes in SendTT and alter your menus until no
conflicting problems remain.
For non-code based ASCII-only, I would recommend a dual menu
system, where you have one set of menus for ANSI users, and
another for ASCII. This would entail having a first menu to
ask the user to choose ANSI or ASCII. But really, it is just
not worth the hassle.
Archivers ARC, LBR, PAK, SHL, SHR, SHZ, Z, and ZOO. Only Archiver
needs to be changed to support these. It is really a minor
fix, couple of additions to the SELECT CASE routines. You
will also need to either program it to shell for the "view
contents" information, or write a routine to get the info
from whichever format you want. Again, I have no plans to
support these formats, primarily because they don't really
compare with what I do support (LZH, ZIP, and ARJ).
I will support any new formats that come out that provide at
least the compression of the above 3.
<Ctrl>Q, I do not feel this is better than [space] and [enter]. These
<Ctrl>S, are commands that are learned at the computer--not calling
<Ctrl>C BBS's. Encouraging people to hit <Ctrl>C unnerves me. The
other two, XON/XOFF flow control, is what I expect for the
computer, but not remotely. I basically think it is a waste,
I mean, most computers nowadays have an actual pause key that
does the same thing.
No message The principle for reducing/eliminating message numbers is to
numbers or make life easier for the user. However, message numbers are
constantly important for record keeping. So, if you're getting up there
renumbered in message numbers, one alternative is Exec-PC's: use a
numbers number/alphabet system. Turning, say, 30xx into Axx, where
xx are message numbers 00-99. This feature is not programmed
in, but it is not that hard to add, a simple substitution.
The authors This is useful for finding out who sent an anonymous letter--
real name for message areas whose mail you allow to be anonymous. I
message field believe that if you want to set up a message area to be
anonymous, then it should be just that. Not just "anonymous"
as the sender, but also "any name goes" for the sender, if
this is what you want to allow, then stick to it--if you do
not like and want to break the privacy bond, then you should
not have set it up as such in the first place.
Generating a This offers increased security over having the user enter
password for their own password. It also requires that the user keep a
the new user note of the password, either on a piece of paper or in the
Communication program's password field. Thus it is an
inconvenience. Use a minimum password length for better
security. With this software, 5 is the minimum to halt a
hacker (the password system is tested a lot by users looking
for other accounts to use--something about automatic name
detection seems to encourage them). This software has many
built in protection against password hacking, but if a user
leaves an obvious password (like their first name), they must
want others to use their account (I make no special
provisions for user or sysop ignorance).
Threaded I do not like them. I find implementations of this to be
messages confusing to me as a user. Yes, they are needed on long
message streams, but are often screwed up by users entering
messages into the middle of the stream (which then get tacked
onto the end) and by users starting new streams with the same
subject (or similar) because they did not want to, or could
not, enter their reply while reading the stream. Or simply
threads getting off track from where the subject they are
for. I will leave the adding of this "feature" (a "pain" in
my book) to someone else. Basically, you will need to expand
the message header record to include two fields: containing
next message in thread (by message number) and previous
message in thread (by message number), both are long
integers.
Just like working with linked lists. Then just add a couple
of extra commands to your "after message displayed" "menu"
lines (+/- is usually the thread commands used).
One nice thing about threads: it lets delete a whole branch
or tree of messages at once--which can be useful when a
message subject dries up.
Wildcards I go into this a bit in the program itself. There are two
reasons for this, one technical, one philosophical.
Wildcards would require a lot more complex checking of of
totals vs. user stats and the need to check for duplicates
among the files selected. The philosophical reason: that
allowing users to DL lots of files at once encourages them to
stay on for longer sessions. By limiting the number of files
they can DL, if they wish to DL more, then they need to "be
around" when the transfer ends. If the first batch of files
takes, say, 90 minutes, they may elect to call the next day
rather then hang around that long. So instead of a user
staying on, say, 120 minutes, they stay on 90 minutes--
freeing up 30 minutes for another user on that day. Sure,
maybe tomorrow the user uses that 30 minutes, but since BBS's
work on a day-to-day basis (new time stats at midnight) its
better to cause more users per day than less users per day.
One trouble with all this: 9600+ users. So it is logical to
develop a wildcard system, but implement it only if the
caller is 9600+. However, I will still wait for the future
with this, it is still tricky to implement now, and I have
more interesting things I want to add. If all the wildcard
files are in the same area, then the point and shoot system
will do the equivalent.
File point I am adding it slowly--as part of the L&D system. Basically
system it will not be a "pure" file points system. It is purpose
will be to add or reduce value to a file (to get a file
around the regular SL based ratios). Example, setting a
files-points-needed to 0 would be like making the file free.
Colors I do not have any system for users to be able to define the
colors that they see. I feel that the presentation is a
reflection of the sysop--and should not be altered by the
users just because they do not like it. On one hand you
could say that it is one of the things that make BBS's
unique--users being able to alter what they see--but on the
other, no customer of any business is allowed to just walk in
and repaint the place to colors they like. It also happens
that modifying the code for this feature would be difficult,
although for a couple of specific colors it might not be so
tough.
User capture A command, that the user may select, to capture part of their
to file session to a file, that they may later download it. I feel
that this is the responsibility of the user's communication
program.
Script These can range from the simple questionnaire type of script,
Languages to very powerful languages that a sysop can use to add
modules and functionality to the BBS.
Including the source makes a script language redundant.
Since any language can be used. The exception being a
questionnaire script language. My SendTT codes are flexible,
so my survey system is probably good enough--if not, just use
a DataBaser database to do the survey.
Misc. Those things most likely to contain bugs are the stuff I
do not use much on my BBS: File Points, Shuttle Logons,
Multiple Protocols, Doors, Separate File Areas, negative
SL's, etc. For these, I would urge those of you who do
operate BBS's with an emphasis on the above, to let me know
what bugs you find when using this software.
COMPETITION Below are listed the capabilities that other BBS software
packages can do (and were not touched on above), that this
one currently cannot.
It may or may not in the future. A "-" means I do not plan
to have it, a "+" means eventually I will put it in, and a
"=" means I do not know.
To shorten the lists, if a BBS package following a previous
BBS review, has a feature that I do not, but the previous one
did (and is noted) than I will not note it here. The purpose
here is not to highlight other BBS's, but to list other
additional capabilities for this software.
To my knowledge, this is the first comprehensive list of BBS
functionalities, and I hope my fellow BBS authors find it
useful.
Auntie 5.11 =An install program.
by W.J. Meier -Separate docs for user and sysop.
($100) =Most sysop-specific routines, instead of being subroutines,
(18-Jul-91) are sub programs.
-A verify program to check out your setup of the software.
-Script based questionnaires.
+View an archive text file.
+Mouse support.
-Uses BRUNxx.EXE.
+Uses SHARE.EXE.
+Novell network support.
+Integrity testing of uploads.
-Distinguishes between a daily time and a session time limits.
+Multi-node capability.
+Send messages to another node.
+List users on other nodes.
+"Conference room"--chat area among the nodes.
=Changeable chat "handles".
+Option to hide sysop's use on another node.
+Send a message to another node while in conference without
the other nodes being able to see it.
-Context sensitive help and a help menu.
=Searches DOS PATH areas looking for utility programs (vs.
predefined areas the BBS expects them to be in).
-Can be called as a door itself set up sub-BBS's with own
message and file bases.
+Time bank.
+Properly handles RTS/CTS flow control.
+43 (graphic) line mode supported at console.
+Event handling (system shuts down at a time, batch file does
the rest) session time is reduced accordingly.
+Command to "pop" a user into chat mode at the next menu (so
they finish what they're currently doing)--a toggle, should
the sysop change their mind.
+Command to pop-up a window displaying sysop keys.
+Sysop chat.
+Page only allowed during predefined hours.
-A sysop "get attention" beep will go for x seconds, if no
response user is told sysop isn't available.
=^E or <esc> terminates chat (at either end).
+Export (send ascii) file to user while in chat.
-Stop specific users from paging the sysop.
-Threaded messages.
-Reading by thread (vs. sequential/chronological order).
-Jumping to first message of a thread.
-Join two message threads.
-Break a thread.
-Move/insert thread pointers to other message/thread trees.
-Delete an entire thread of messages (prune the tree).
-Send callers log file output to printer.
-True multi-line file descriptions.
-List a range of filenames containing a string or wildcards.
+List top 10 DL's (filenames)--sorted by times DL'd.
+Send file descriptions to a file to DL--user sets
range/search options.
+Disable DL's between certain hours.
-Stop users from doing anything download related (list/etc.)
during this period.
-Give more DL time in off-hours.
-Prevent DL'ing of uploads area (new, untested stuff).
+Summarize the distribution of DL files across the files/drive.
-Unwanted files (filename checker) can include a text line
about why they're not wanted (user would be shown this).
=Message marking for later actions (such as reading,
deleting, DL'ing).
=Mark all messages containing a search string in any or a
few fields as well as the body of text, also by date.
+Option to never update messages to the sysop as having been
received (for "read again" purposes or for the "received on
..." message stopping purpose?).
=Sender may edit a message after it's already been sent,
including: to name, from name, subject, message body, and
message area it's posted in.
+Compress messages into a user DL'able file--user select
which messages either by reading the message (only header
will be shown if have this "on") or by number range, or
simply "all new messages".
+Can select "x back from the latest message posted" when
defining what messages to include for DL.
+List only those messages you sent or received.
+Scanning messages forward or backward, and doing it from
any message number.
=Send message to receiver or sender of the message being
read, may or may not be a "reply" (user decides).
=Editing Messages:
+Re-wrap a part of the message being edited/entered to any
given length (it uses the whole message, but this is good
idea for use with single paragraphs too--just provide a
starting and ending column, or a starting column and a
length, or merely a length (assumes start from 1st col) and
re-wrap that portion of the text)
+List message lines by range (n1 to n2) of message being
entered/edited.
-Set right margin for messages being read/entered.
-Quote only a specific range of lines from the message
being replied to.
-Global search and replace of all occurrences of a string.
-Strip 8th bit (for UL'd Wordstar files).
=For cc:'d messages, only one copy of the message and a
header for each person sent to is stored.
+Read the parent message while editing a reply (re-read the
message you're replying to).
+Reply to messages without reading them first.
+Auto deletion of old messages.
+Auto deletion if there are too many messages on-line.
+Option to kill all private mail which has been read by the
receiver.
-Dumps message text to printers.
+Ability to stop a message (via a flag in header) from being
echomailed out.
=Reset high message pointer.
+Flag to stop various auto-delete (user and message) routines
from removing a specified user/message.
-User record flag/option: skip over messages they sent.
-Flag to determine whether user should be charged only for DL
time, or for every minute using the system.
+User "rating's" based on formula.
+Automatic actions based on this rating (reduced time/DL
limits/etc.).
+Data on how a specific user used/uses the system.
+Mandatory login (new user) questionnaire.
+"Autoskip"--skip old logon stuff (ansi's etc.) after x
logons.
=Supports subscription terms (dates).
+Utility to convert info in users file to a regular text
file.
-Sends only CHR$(8) to backspace, CHR$(12) to CLS, and
optional extra linefeeds.
+Increment a number (eg. xxxxxxyy where yy is the number) for
each extract or message download file the user creates, thus
allowing the user to DL each new file without worrying about
overwriting the previous DL.
+Auto screen clearer when nobody calls after x minutes.
+Statistics on the callers log.
+Shows a graphic tree of the structure of your message base
(don't know if this is areas, or messages/threads).
=Keeps size of input buffer on status line, when it exceeds
300 chars, it assumes something is wrong and hangs up (like a
bad UL).
-Renumber message numbers.
+Summary of callers log includes: unknown entries, illegal
logon attempts, user timeouts, uploads, downloads, protocols
used, new callers, how many have ANSI, how many have MNP
modems, average number of callers per week and per day,
average call length, how many minutes used by each protocol
type, how much time with messages, number of messages left,
number of doors opened, number of carrier losses, average
number of downloads per call, number of attempts to chat
with sysop, number of errors.
-Can set a delay between individual characters outputted.
-"What's hot" (top DL's) report can require a minimum number of
downloads before being considered.
+Give statistics of the file areas (number of files, number
of bytes, percents of total, averages, totals).
+Keeps track of when user last used "new files".
---Conclusion:
Auntie is a very good BBS system for message handling and
statistics.
Spitfire 3.1 -Can sequentially page thru user records with +/- while
by Mike Woltz waiting for a caller.
($85) -Command to log a caller out with a message.
(24-Jun-91) -Command to log a caller out without a message.
-Command to toggle a callers lock-out status while they are
on-line.
=Uses COMSPEC instead of DOS PATH to find where COMMAND.COM
is (for shelling).
+Prevents using a door if user has 3 or less minutes of time
left.
+A pop-up window containing the toggle-able sysop stuff.
-Display a file when user time-outs (not just hang-up).
=User is "beeped" for various things.
-Toggle whether the result codes (eg. connect 2400) are shown
when they're received.
+Supports net-mail.
=Flag in message header if a message is net-mail.
-Add a tag line to all net-mail.
+Purge old messages based on date (days ago).
-Supports use of a front end programs.
+Events:
+Events can be set for any day of the week, or any
combination of days of the week.
+Option to not do event if the BBS was busy at the time.
-Improved Xmodem termination.
-Makes files read-only before calling protocol, and back to
their normal state after protocol returns--to protect the
files.
-At log on caller notified of new mail, total messages they
sent/received and total messages active on the BBS.
-At log on, user can list all new files, and is given total
files available for DL on the BBS, and number of new files
since last call statistics.
=Automatically converts 1st letter of descriptions to
uppercase.
=Can use birth date confirmation as a second password.
=Can write directly to the screen.
-Command to toggle the printer when user on-line (or not).
=Maintains daily statistics that can be viewed with a
command.
-Command to toggle a full or divided screen when a user on-
line.
+Sysop can display callers log from today's first entry on, or
the whole thing, or specify a date.
-A separate "callers log" for sysop alert/"take notice" notes
(bugs/etc.).
+Make a bulletin of the previous weeks' callers log info
(based on).
+Can put part of itself in EMS.
+Can limit the number and length of inter-nodal chats.
+Has a "lockout" list of file names user's can't upload.
+Can automatically purge messages older than a certain number
of days.
+Sysop hot-key to check today's stat's so far.
+Sysop hot-key to remove backup and log files (when caller
on-line or not--instant free drive space).
---Conclusion:
A complete BBS system. Reminds me of my own product, but
without all the high-tech.
Minihost -7 bit communications operations.
Release +Ability to limit access to files areas of which user has the
08/01/87b same SL as the area (not greater, not less)--allows for
user-specific file bases.
by Don Mankin -Can tack new messages on at the top of the message file
($25) rather than the bottom.
(2-Aug-87) -Ringback--user calls twice in 10 seconds to log on. Sysop
can answer phone, if carrier, then hangs up, if person, then
talks.
-Description entry "guide line" has marks as to position
length (marks off 10, 20, 30, etc.).
-DigiCOM4/8 (?) support.
---Conclusion:
Started life as a remote access utility, still pretty much
what it is.
RyBBS +Internal communications program:
Version 5.0 +Own help screen.
=Auto-dial menu.
by +Function key assignments/macros.
+Script support.
Gregory Ryan +Allows users to define macros (stores them, user may also
($45-$175) redefine previous macros they defined).
(29-May-88) =Maintains information on the current user on-line in it's own
file.
-File containing list of files not to be downloaded.
+Send a personal "file" (text file = message) to any user
(nnnn.txt where nnnn is the user's "number").
+Display it, then automatically delete it.
=User records have toggliable flags for when they've read
corresponding bulletins.
-Can restrict UL's to have only .ARC extensions.
+Can display a text file in reverse.
+Sysop can send a command to another node to be executed by
that node.
+Sysop can sneak a peak at the other nodes' screens while
calling remotely himself.
+Menu command to reboot the computer.
+Can set menu selection with conditions so that when they are
met (key stoke hit by a user with a certain SL) an entry in
the log file is made.
+Menu option to summarize what each user is doing on each
node.
+Allows BBS to send commands to another window of a mutli-
tasker (programs to run, etc.)
+3 types of events:
+Hang up user, shut down BBS, and do it.
+Send it to another window (multi-tasking) to be done.
+Shell to dos to do it (by shelling, you can tell user to
"hang on...").
+Can prioritize events.
+Sysop can display users info whenever on-line or do it for
the "last caller" from the waiting for caller screen.
+Can read callers log in forward or reverse.
+While in chat, sysop can disable full duplex (helpful when
user jumps to DOS and dos a CTTY COM1).
+If one node is dormant and multi-tasking, gives the other
node extra/unused processor ticks (under DoubleDos).
---Conclusion:
An emphasis on programming with a menu "macro" language.
IronHenge +Wording: "rooms" instead of "message bases" and "file areas"
Version connected by "hallways" (rooms are lined down hallways--a
2.41a.05 technical hallway contains all the technical-related message
bases).
by +Wording: "food and drink for you to take with you or which
you may leave to share with others"--file areas,
Caves of downloading, uploading.
Chaotic =Wording: "lobby" for main menu.
Silicon -Shares messages and files with other IronHenge BBS's.
+Can organize message bases and users into independent and
(Free) overlapping sets.
(1-Jul-90) +Circular message base: old messages are deleted as new ones
are entered.
=Has a config field for what time zone you're in.
=Has a config field for "region" (state or otherwise).
=Routes network mail not to your BBS to a "dead letter"
message base.
=Show system usage at logon to users every x calls.
=Stats: # of calls the system has taken since the user last
called.
=Stats: the amount of time since the user last called.
=Stats: the number of users that have called since the user
last called.
+Can configure how dates and times should be outputted (using
a formatting system)(like print using does).
-Can limit the amount of "k" each message base uses.
+Can define maximum number of bytes to allow in a message.
+Can define what is to be logged and what isn't.
+Can set maximum messages a user can leave per call.
-Can set maximum number of times a user may try sysop chat in
a session.
+Can set number of nulls (delay) after each CR/LF is sent.
+Toggle whether "read new messages" should include the last
oldest message (new - 1)--to help refresh memories. (user
toggle?)
-Option to auto create a new network node entry when another
node contacts the BBS.
+Can create "rooms" in the "hallway" you're currently at.
+"Private rooms":
+That don't even echo at the console--private from the sysop!
+Once one knows they exist, and go to them, then they can
access it, otherwise NOBODY except the person who created
it will know about it (they then can tell their friends)
Once found, the room will appear on their lists of message
bases (for new message searches, etc.).
+Can be shown a list of users who know about the private room.
+You can have "group only (public and private) rooms"--groups
are a collection of user names.
+Can have/or have not group rooms messages's be read by all
(but only left by members of the group).
+Multiple "file rooms" can share the same drive/path.
+Can prevent the release of inter-network mail until sysop or
"aide" (co-sysops?) "releases" it.
+Can prevent callers from entering any keystrokes (by you
still can) (toggle).
=When doing listings, user can type "J" to "jump" to the next
paragraph (such as when listing messages).
-"Dot commands"--a "." brings up a prompt from which you
enter cmds w/o two or more letters (eg. .ER<CR>).
=Enter a message in a "room" by "just typing the text" after
entering the room (scrawling on the walls?).
-Message entry relies on users comm program to do
wordwrapping.
-Can list all groups to which the user belongs.
+Networked messages keep track of the number of "hops" they
did (the number of nodes they've passed thru).
+List all rooms in a hallway (all "known" rooms) (with
breakdowns by room type and new messages).
+List all hallways that connect with the hallway the user is
in.
++/- keys page thru the rooms in the hallway (the message
bases).
+</> keys page thru the hallways.
+A "sysop's hallway" contains all the rooms (linkages to)
(like a sewer system).
+Can have group only hallways.
=User can keep their name from being listed in the user log.
+User can set what "hallway" they start in at logon.
+User can forward messages to them to another user
(automatic, for when the user expects to be away for
awhile). User sets who the message is forwarded to. Can
forward to another network node as well. Can keep the fact
that the message was forwarded secret from the sender.
+Stats has average message length.
+Break down of total # of messages by type: public, private,
net, in-transit, outbound, group-only, waiting for sysop
outbound approval, and SL/type of user who sent.
+Stats: average message chain length.
+Stats: counts of characters sent and received during the
current users session.
=User can log out but not hangup (so more then one user at
the same computer can logon without calling back).
+User can accrue (add up) time credits by not calling (+ x
minutes for each day since user last called).
+Sysop can set it so that a group's members can only call
certain days of the week (eg. MWF).
+Sysop can set it for a group's members can only log on
during certain hours.
+Can set time limits for groups as a whole.
+Different values as to what a "time unit" is can be given to
different groups (or baud rates).
+User gets additional time credits proportional to the number
of callers that have called since his last logon. Since
more callers means less accessibility and more messages to
read (if time for reading messages is subtracted from users
time).
+Can keep track of characters sent to a user (for
cost/charging purposes). The idea gives users credits for
entering messages, and takes credits for reading messages.
"This combination can encourage users to participate in
discussions and weed out those who are taking and not
giving." (think the second part is for files, not sure).
+Can keep track of characters received from user for
cost/credit system.
+Can set up credit system that applies factors based on time
of day (less credits in busy time, more at night, etc.).
+For transferring networked messages, a file is maintained
containing corresponding message bases and groups. For
instance, the base could be "for sale" on one BBS and
"classified's" on the other, this file would make note of
that fact.
+Can set (individually) how often to automatically call and
exchange with another BBS.
=Command to read new mail in reverse (new to old).
+Can enter messages to groups (give part or all of the name
of the group). Message shows "TO: <groupname> only" when
scanning.
+ H O N E S T D I S C L A I M E R
Whereas we/us guys wrote, borrowed, snatched from the public
domain, or otherwise created/generated/hatched IronHenge as
our/ours principal projected means of paying for an
occasional round of drinks, and whereas you/youse guys are
using IronHenge for whatever reason you alone shall
determine as being sufficient, and whereas since we live in
a capitalistic state and since you know it's a crime to
duplicate this stuff, but/and even if you didn't know it you
do now, and whereas even though there may be more than one
of you/youse, each man/woman/unit should send us your
checks, your Visa cards, and/or your money orders in
whatever amount you/youse deems acceptable somewheres in the
monetary range of between 5 (five) and 500000 (five hundred
thousand) dollars American, wherein it shall also be known
that regardless of the amount that you/youse shall
contribute to our/ours drinking fund, the amount of support
shall remain non-existant.
Now therefore we request that you/youse don't abuse the fact
that we/us have not copy protected this software nor have
we/us required you/youse to have a special super secret
decoder ring to produce/print/read this manual.
And also whereas the PC/clone is a complex whizbang
computer, and Murphy was an Optimist, let it also be stated
by we/us and understood by you/youse that, although we have
stayed awake late at night, and in some cases because we
have, that this software may on occasion do things that
neither you/youse nor we/us may have anticipated and in the
majority of those cases it shall cause you great amounts of
frustration.
But nevertheless let it be agreed that in using this
software our liability shall be limited to the great
embarrassment we/us shall suffer no matter what your lawyer
shall lead you/youse to believe to the contrary, or at the
very worst we/us shall have to invite you/youse to our next
annual summer bash.
And finally, whereas in spite of all our claims that
IronHenge can slice, dice, and chop your text, message base,
and even binary files and all those other silly advertising
claims our marketing department comes up with, it is up to
you/youse to figure out what IronHenge can really do and
whether or not it is suitable for your particular
needs/wants/wishes.
Caves of Chaotic Silicon
15 Central Way
Suite 384
Kirkland, Washington 98033
+The barrier of discrimination, in the conventional sense, is
not a part of the bulletin board world. No one knows your
race or your gender, or if you are differently abled (i.e.,
deaf, physically disabled, etc.) when they read what you've
typed. The only judgment that occurs is made based upon the
value of your words.
Users have the freedom of being anonymous, of indulging in
the fantasy of being the "mysterious stranger." One is free
to say what they wish to, not held to any expectations or
conventionalism. There are occasions when this has been
problematic or somewhat ridiculous, but in a world where
most of our time is tempered by the expectations of
normalcy, it is refreshing to break away from whatever
stereotypes or images haunt your life.
Users also have the opportunity to share their ideas and
opinions with people they might not meet otherwise. Truly,
the only common denominator is the fact that all users have
access to computers. Computer programmers, homemakers,
bikers, executives and high school students all faithfully
enlist their autodialers and bang away at their keyboards,
day and night. Each user has a forum for their voice to be
heard without having to shout over the voices of others.
It's equal opportunity and non-denominational. All learn
about the world around them and, indirectly, about the human
condition from each other. I enjoy witnessing this
communion between individuals who are so unique and diverse.
As a sysop, I offer the following "simple" caveats to all
who will be running this program. Carefully define what you
think is or is not appropriate on your bulletin board, and
clearly communicate these boundaries to your users. Think
freely. Laugh often. Accept that correct spelling and
proper grammar are subjective and creative concepts.
Exercise patience and tolerance when necessary. Grow.
Experiment and be imaginative. Be curious about those who
call your board. Make some mistakes and learn from them.
Have faith. Explore the unknown. Celebrate life and the
people around you. Remember that the bulletin board exists
for the users, but don't ever let them scent your blood,
sweat or tears. Ah, yes -- don't forget to invest in
quality equipment to run this fine program you've just
acquired. The reliability of your hardware may be all that
stands between you the doors of your local asylum. Just do
the best job you can. I know it's not much, but it's all
the wisdom I have to impart to you at this time.
Time carves changes into our lives. People pass through
the revolving door at the entrance to our heart. Technology
occasionally threatens us like a possessed steamroller. In
a world of talking teddy bears and computer controlled
automobiles, I am thankful for this window into the human
spirit. I wish you much enthusiastic adventure and
discovery while using IronHenge.
--Lauren Guimont
--Conclusion:
Imaginative, can set it up to look like a house, or a small
town. This is a program worthy of continued development, and
should do really well in a graphic BBS future. It's strength
is it's message bases.
TurboBBS -Stores each message as an individual text file.
Version 8502 =Keeps a user comments file (short 4 line
feedback/hints/etc.).
by -Supports WordStar text formats (in bulletins, etc.).
Robert H. -File record has field for whether the file is public or
Maxwell private.
& +Keeps a count of the number of times text (eg. individual
Donald W. Mack bulletins) have been displayed.
($45)
(24-Oct-85) ---Conclusion:
An ancient and primitive BBS from the very earliest days.
Searchlight =Full screen text editor.
BBS v 1.31 -WordStar compatible editing keys.
-Can use to modify all data input.
by =Can edit small text files and create new text files (max =
250-400 lines).
Frank LaRosa =Users can add to the quotes file.
($35-$95) =Users can post bulletins (actually a special message base
(26-Sep-91) with a different format).
=New ones displayed automatically when log on.
-Has an 8 slot circular method, after 8 each new bulletin
causes the wiping of the oldest. Does have a flag you can
set to protect it. 8 to emphasize to all that they are
supposed to be important.
=Any key continues after a pause or 24 line screen full pause.
-New users type "new" to log in.
+File records have a password field--to be cleared after
sysop verifies the uploads.
+Password protected files also allow two users to exchange
files privately.
+Modem init string: ~ for delays, ! for CR/LF's.
-Users can log in as "guests".
-Sub-sysop's/sysop's (of their own message base) can edit any
messages after they've been saved.
+Flag to protect individual messages from "mass" deletion
functions.
=User info screen allows editing of it's fields by moving
around with arrow keys (user and sysop).
+Forwarding done from read messages, can forward to another
user, or to a message base, or sysop can also send it to a
text file.
-List users:
=Can enter just a couple of letters, and it lists all names
from those starting letters on.
+Each message base has an "access level" field, and maximum
message length field.
+When user on hot key: to page thru a variety of "sysop
lines" at the bottom of the screen.
+When user on hot key: send all I/O to file or device:
Automatically removes backspaces and ANSI control codes.
Also works where ever you go (including door and dos). Any
text that normally goes to the screen will show up in the
file.
+"File inclusion": putting "%%filename.ext" or
"@@filename.ext" on it's own line in a message will cause
that text file to be displayed (only) when any user reads
the message (but not when editing).
+Can "swap" two message bases.
+A "+" is next to each file in the listing that is password
protected.
="Scroll" thru a single line "menu prompt" by using the
backspace key and spacebar to select (for such as read
messages options, etc.).
=Can list files with wildcards or "from these first few
letters on". ("L" gets L - Z, L*.* only gets all files that
start with "L").
+Internal routines to send any "door type" operations to the
comm (without needing CTTY etc.) Does DOS.
+Can disable this for doors that have their own comm support.
+Door routine lets you use the command line to output various
info to the door (metacommand parameters).
+Automatic logging of sysop mail (sysop toggle) to disk.
-It's BBS programs are treated like doors, the heart of
Searchlight is a TSR that intercepts the interrupts.
---Conclusion:
It's "umbrella" method of communications is quite powerful.
This wasn't their "extended version" of the BBS. It's a well
thought out beginning sysop's BBS.
OmegaBBS -Remote mouse capabilities (using a special driver on user's
Version 1.04e end?).
-Sub-boards:
by Rick Harris -Up to 250.
($80) -Password protected.
(4-Aug-91) -Can have 200 message bases each.
-Unlimited number of file areas per sub-board.
+Split screen chat (sysop and user can type at the same
time).
+Sysop on next: pages the sysop when user is done (as well as
takes the phone off the hook).
+"New stuff" option allows users to configure it to
include/exclude areas (message and file).
+Multiple file searches (up to 10 partial strings).
+Search file names, descriptions, or both.
+3 levels of archive/upload testing:
+None.
+/t (eg. pkzip /t).
+/t and virus check of each member file.
+Can configure it so UL's go to a RAM disk, where they're
tested then moved to an area.
+Files that fail testing can either be deleted or moved to a
specified area.
+Will re-compress files to an archive format (zip, etc.) and
give the user credit based on that size (after compression).
+Post/call ratio support.
=Sysop can use mouse to work and move files between areas.
-Own script language.
=COM debugger routines.
-Users have ID #'s.
-Can't leave messages to yourself.
-User record field for Bad exits.
+Sysop-only uploads are moved to a "sysop only" download
area.
-It's script language is a lot like programming in C.
=Does backward scroll of file lists--provided user is using
Nansi or Zansi, or the like--only ANSI drivers that support
calls fro inserting lines on the video screen.
---Conclusion:
This has the look and feel of a "corporate product". The
mouse thing is quaint, but it's script could make it a
powerful contender in the future, providing it can attract
programmers.
Radioactive -Sends a message to users who hang up incorrectly.
Telegard BBS +Log informs:
2.6b +When a user was given the shuttle password.
+When a user hasn't been validated yet (tried to find out
by shuttle password).
+Can set it so users can only log on once per day (x per day).
Michael A. +When logon, informs you if your mail is being forwarded to
Smith another user (for vacation thing).
+User info lists user's age.
(Free) +Says "happy x day" for the holidays.
+Add comment fields/files to archives.
+User info lists user's file points.
+Maintains a temporary directory where users can leave text
files for each other to see.
+Can use REZIP (or a similar utility) to re-archive UL's.
+Can convert all non-ZIPs at once (in all directories).
+Gives numbers: number of archives converted, space
saved/space wasted, old total space and new total space
used by the archives.
+Think it may show the above number's for each archive after
conversion/during conversion of each archive as well.
+Can merge files to create a new archive member.
+Time used for conversions from one archive format to another
is subtracted from users stats.
-Can DL files giving only their ID number.
+Can validate messages.
-Can strip colors from messages.
="Any name" messages allowed (use any name as the message
from name)
+Keeps track of how many days the callers log contains.
+Sysop can view callers log by specific date, or from x days
ago on.
+Can create file directories on-line.
=Can set a pause period before each menu is displayed (for
each menu).
+Fidonet mail:
+Strip IFNA kluge lines.
+Strip SEEN-BY lines.
+Strip origin line.
+Add tear/origin lines.
+GroupMail support.
+Can set maximum allowed file size a file base.
+Can set minimum file size needed to allow a resume (to not
delete partials).
+Can configure SL's so they:
+Can't page sysop.
+Mandatory mail deletion.
+Can "undo" a users record after exiting the user modify
routine for that user.
+Deleting user automatically deletes any e-mail user sent or
received.
-Can have "tailored" or individual lockout files--displayed
before hung up for users you lock out.
-Has "fallback" menus in case the primary menu file is
missing.
+Can limit the number of messages posted per day (for each
user and system).
+Can limit amount of mail a person may have active at once
("how full their mail box is"--to encourage deleting).
+Can limit the number of feedback messages posted per day (for
each user and system).
+Gives a log summary of the days statistics (posts, files,
calls, new users, etc.).
+Can limit the size of extracts user does (and total
extracts).
+Sysop key to hang up user, but before, sending them one of a
variety of text files.
+User can open/close/forward their mail box--closing stops
all incoming mail.
+Shuttle:
+Chat with sysop (sends e-mail if not avail).
-An "emergency sysop page" (not on menu?).
+Can fake line noise and then hang up (sysop key for this).
+Can toggle sysop information window (my "user data line")
on/off.
-Message editor has command to center the line of text.
+Ability to pack only one message base.
WWIV v4.20 +Can restrict individual users from posting.
by Wayne Bell +Can automatically send an individual users uploads to the
($50 - $55) sysop dir.
(14-Aug-91) +Can restrict individual users from using net-mail.
+Automatically checks to see which ports have modems during
configuration.
+Automatically determines maximum speed of the modem during
configuration.
-User record has field for "gold"--used in on-line games, to
provide an "award/punishment" system.
-Monitors scroll lock key as an override to whether the sysop
is available for chat.
+Hotkey to answer phone and send carrier (for when talking
voice and decide to go data with that user).
+Can list last 77 network connections (for net mail).
+Sysop command to rename a file.
+Message base has "minimum age" record.
+User record bit to force user to enter birthdate at next
logon.
+User record bit to stop user from using automessage (to
another user when logoff).
+Can edit new lines into text files.
+Can have the BBS send a message back to the user saying his
letter has been read.
+Automessages are short 3 line comments other users see.
+Can be replied to.
=When at a mail menu, hitting +/- or </> will move you to the
next/previous message base.
+Instead of a "date" in "date sent" it has "x days ago".
+NetMail has an "estimated cost per minute to get the message
there"--think it calc's based on size and number of "hops"
and baud rate sent at.
+When a users enter's a macro, it shows what's got (what it
found acceptable or max'ed out at) and asks the user if
that's what they want.
-Has in message "/" commands that do things normally done
from an message entry command line.
---Conclusion:
It's pretty restrictive as to it's limitations and what the
sysop can do or change. Registration will get you the source.
It has a nice "gfile" (general text files) system.
WILDCAT! +Asks user if they would like a note confirming that the user
03/01/91 TEST received the messages.
DRIVE -Deleted messages get put into a "deleted messages" message
base.
by +Wording: "event" is "scheduled maintenance".
-Can branch from one questionnaire to another.
Jim Harrer -Asks users if they want to continue anyway (after being
informed of an approaching event.)
($135-$505) -The original uploader of a file may overwrite it with
(1-Mar-91) another upload of the same name.
-Can set a minimum SL to allow overwriting when uploading.
-For a closed system, can force caller to leave a message or
answer a questionnaire.
+Toggles to task for user's phone number, birth date, and/or
computer type at logon.
+Can set it so phone number and/or birth date must be re-
verified (like password) every x logons.
-Can force the system so the sysop must view/validate public
and/or private messages before anyone else can.
-Can not display password protected files in files listing
(thus, a user would be told the file exists, and its
password).
+Option to print out the users database info to a printer or
file.
+Option to delete the log file.
+When-user-on hot-key: when user logs off, take phone off
hook and go to DOS.
---Conclusion:
A fairly complete BBS. Kinda old. Not a lot of frills. Too
expensive for what it does. Too limited.
Professional +Wording: "events" are known as "tasks".
OLEcom +Password field for messages.
Version 3.0a =Menu record has field for how many times a menu was
displayed.
by John T. =Menu record has fields for start/end of access period
Oleson, Jr. allowed to this menu.
($65) +A flag in the message header record that makes a message
(7-Feb-89) invisible except to the sysop.
---Conclusion:
Not much to say, another out-of-date BBS program.
UltraBBS +Allows users to enter single word names.
Version 2.02 -Door record has password field.
-Voting questions has a password field.
by Bob Farmer +User record has field to "automatically send user to a
($75-$90) specified door" when they log in.
(29-May-91) -User record has field for what their SL will become after
their subscription period expires.
-User record has field for what their "allowed message bases"
will be when their subscription period expires.
+Won't auto-add .GIF resolution if it already senses it in
the description.
+Supports ANSI music.
+Can answer on the Xth ring instead of the first.
+User record has field for total number of minutes user ever
spent on the BBS.
+User record has field for filename to display to user upon
login.
+User record has field for "autopage sysop" when user logs on
(options: None, Invisible page, Visible page).
---Conclusion:
Lots of user settings to customize their session, very
powerful if properly implemented by the sysop. File attach
capabilities are quite nice also.
RBBS-PC +Personal downloads, can set it so a file can be DL'd by a
release 17.3A specified user or group of users.
+A "questionnaire menu" giving descriptions of the various
by questionnaires available, user can then select one to answer.
D. Thomas Mack A menu of questionnaires, and bulletins.
(Free) +Automatic sysop page: can be done when a user logs on, a
(26-Aug-90) member of a group, or when a user enters a specified message
base. And can have the computer return with a little note
as to what the reason for wanting to chat was (it's
displayed only to sysop as the computer calls for you).
+Can automatically send a warning message to the user if
their subscription is about to expire.
---Conclusion:
It's the most well known of the "source included" BBS's. It
needed to be modernized about '89 or '90, now it's perceived
as too big and klutzy for modern BBS'ing. It's the preferred
software for big BBS's.
Telegard -Menu's have password fields.
Version 2.7 +Sysop can activate/deactivate defined protocols.
=Can store messages in their own directory (for each message
by base).
+User can toggle so they don't receive mail.
Eric Oman +Sysop can delete all the email of any user.
+Does a "you had a birthday since your last logon." and
and "happy birthday today" and "you turned xx today!"
+Beeps user (sysop toggle) just before time-out.
Martin Pollard =Can it so it compresses file/msg numbers.
+Can toggle on/off the UL duplicate file search.
and +Guest user has it's own record (like my new user record, or
a user of the name GUEST).
Todd Bolitho +File point system.
=User record has restriction field for:
(Free) can logon only once per day
can't page sysop
posts marked unvalidated
can't post send anon
can't post at all
can't send email
can't vote
automatic mail deletion
no UL/DL ratio ck
no post/call ratio ck
no file pt ck
protection from deletion.
=File bases have fields for: name, filename, dl path, ul
path, maxfiles, password, arctype, comment type,
hidden/gifspecs/no ratio bits, and group ACS setting
limitations.
=Can output a user's caller's log/session/trap chat to it's
own individual file.
=Message bases have fields for:
name, filename, last msgid, msgpath, ACS, POST ACS, max
msgs, anonymous, password
netmail: zone, net, node, point, origin, text color, quote
color, tear color, origin color
flags for fidomail: skluge, seenby, orign, center, box,
addtear, mcenter
=File bases has field for : age requirement, archive format,
gif specs yes/no.
=Can trap the session or chat session to any filename when
you toggle it on.
+Can go thru and mass-update all the archive comment fields.
+Can change BBS colors "on the fly" by filtering the codes
thru color translation tables/files.
+When working on a user record (ie, SL level) can select F1
to do it and show user "Sysop working", or <shift>F1 to do
it and not show the message.
+Sysop key to disable user input (without disabling the
console's).
+Sysop key to send CHR$(7)'s until user presses a key or
hangs up.
=Powerful "ACS" conditional language for menu options.
Forum-PC 2.5c +Bulletins:
+Print's out the last date they were updated.
by +Record has fields for: SL, File name, and title.
-Keeps track of last bulletin user read.
Kenneth J. =Automatically deletes first 5 messages when reach maximum
Duda messages allowed.
-Wording: "message-op"'s are "sponsor"'s.
(?) -Sub-board record has fields for: sponsor, title, number of
(2-Mar-89) bulletins, last read number, number of files
+News file has x number of entries/slots. (keeps track)
+Command to set the system date and time.
-Can view the system log one caller's session at a time.
+Keeps track of the number of days the BBS has been up.
+Statistics for: calls per day, total minutes in use, total
minutes idle, minutes doing file transfers, total minutes
up, total minutes down, % in use, % idle, % up, % down.
+Has (co-)sysop fields for: file transfer, bulletins, voting
booths, e-mail, doors, menus, databases. These in turn
break down into x records.
+Can limit the number of feedback messages a user can post
per session.
-Files can be accessed via their number.
+Can rename files.
+Can re-order file areas (record numbers).
=Can lock-out certain protocols during a time period.
=Can easily add choices to voting questions (users and
sysops).
+Can set the max limit on number of voting questions, number
of voting choices, number of persons per group.
+Groups of users can be: Public, Private, and Personal.
+Group definition record: group name, title, sponsor, number
of members, each member's record number
+Creator of the group need not be a member of the group.
+Can mass add or delete by group or level: access to boards,
or groups, etc.
-Editing messages:
-Search and delete with Y/N verification at each one.
-Redo the subject field.
-Clear the message and restart from line 1.
+List all the users who have a birthday today when login.
+Lists special events for today when logging in.
-Can just enter your user number to log in (no name).
+Internal comm program supports scripts.
---Conclusion:
It's old. Some good ideas in the way it handles co-sysops,
groups, and bulletin/text files. Terrible message system.
ViSiON v0.82 +Shows percent of total users who voted on a question.
=Doesn't show current vote totals until after they vote (not
by influenced).
+Can add more vote questions on-line.
Crimson Blade +Can remove choices on-line, automatically update's records
of those who voted for that choice.
& +When editing mail: can select to abort/abandon all the new
changes.
The Elemental -Can keep a "split screen" up--half showing the callers
stats, the other half the users' session.
(?) =Sysop when-user-on key to "lock the timer".
+User rec keeps track of g-file UL's and DL's.
+Can do group editing from reading mail.
+Can set a bit so that a file needs special permission from
op to DL.
+Can edit a user rec from chat.
+Can chat by splitting the screen down the middle--vertically
or horizontally.
+Stats include:
+Best post/call ratios.
+Worst U/D ratios.
+Worst post/call ratios.
+Best U/D ratios.
+Users can give file points to another user.
+Users can take file points form another usr: provided they
subtract it from themselves.
+Can restrict file transfers if their baud rate is below a
certain number (logon @ 300, but not DL, etc.).
---Conclusion:
This is an enhancement of the Forum-PC software. More screen
related stuff, netmail support, and other stuff. Still fairly
primitive but many reasonable ideas.
ICP v. 303b This is a hack job--some child just replaced all occurrences of
"WWIV" with "I.C.P.". A pathetic individual.
Socrates BBS +Can limit number of DL bytes per session.
System v1.10 +Can limit total number of DL bytes a user is allowed (all-
time total).
by +Can limit number of DL files per session.
+Can limit number of DL files a user is allowed (all-time
Michael A. total).
Jacobs +Can set session, daily, and life-time DL:UL file ratios.
+Can set session, daily, and life-time DL:UL byte ratios.
($40) +Maintains a separate index by subject to provide "subject"
oriented messages which can be handled like threaded
messages), when reading, can "skip" subjects and all their
related messages.
-/1 command line switch to say "run once" (for running after
a front end).
-Can limit the time of the user in the command line--thus
knocking the user off before the next front end event.
+When-caller-on toggle to turn on/off the console KB (only
valid sysop keys are accepted if off--no "typing for the
user").
+Can define a string to be sent to user after exit chat.
---Conclusion:
More flexibility designed than many BBS's, but has very few
frills. It's flexibility comes at the expense of
complexity--like mine.
T.A.G. +Holding the shift key down when logging in bypasses all the
Version 2.5c logon files (ansi files, news, etc.) for the sysop (but an
idea for users too).
by +Can display an ansi to those with birthdays.
-Can display a file/ansi to those who page sysop more than
Robert maximum # of times.
Numerick =Displays files (1..9) when the same user logs on after just
logging on. (1 being normal, etc.)
and =Most everything that would normally get a "warning" or
"can't do" or even informational message is instead it's own
Victor Capton text file.
+Trashcan file has ability to send a file if a "*" leads the
(Free) name.
(21-Sep-89) +Call back verify makes sure the phone number entered is not
that of the BBS.
=Can set maximum # of messages allowed to be waiting for a
user.
+Phone # check for extra verification--useful to eliminate
users who give phony phone numbers, as they'll have trouble
remembering them.
+User record flag: can't change auto-message.
+User record flag: max of 1 call per day.
=User record flag: can look at votes but not vote.
+Uses "--" to subtract from, and "++" to add to, for numeric
inputs.
+Can group/list together users by their statistics (# of
calls, DL ratio, etc.) using set (mathematical/logic)
commands.
=Rejection of password if it's contained in user's computer
type, phone number, zip, city & state, address, name, or
handle.
---Conclusion:
It's more complex than it need to be. It lacks any frills,
so it's not a heavyweight, but it does have the best
flexibility with regards to displaying text/ansi files for
very many things.
FeatherNet -Can toggle the beep (for chat) on/off separate from
v3.04 availability toggle.
by Ron Pierce =Does search for names by soundex.
($75-$100)
(29-Apr-90) ---Conclusion:
A lightweight BBS program. Quite limited, and perhaps a bit
too confusing for beginners.
QuickBBS +Can have 5 alternate net mail addresses for your BBS.
Version 2.64 =Can set new user's SL to 0, which means locked out, to
provide private (pre-register) BBS.
by +Menu creation: can simulate the menu.
-Send a ^E at first to initial some communication programs'
Adam Hudson auto-logon routines.
& +Command to kill all received messages in an area(s).
The QuickBBS +Command to "move" all messages in one message base to
Group another message base.
+Command to kill all messages in an area(s) that are more
($45-$65) than x days old.
(19-Feb-90) +Command to mark as deleted all messages in an area(s).
+Command to change all messages in an area(s) TO: ALL.
+Can toggle off/on showing of a particular node in the SEEN-
BY lines. That is, can stop the showing of a node address
in the SEEN-BY lines of messages.
---Conclusion:
A basic BBS. More advanced in netmail than normal. No
frills. Progenitor to RA.
Virtual +Max number of attempts to connect to another BBS (net send).
BBS/NET +Supports H/S Link for .PKT transfers.
Version 5.41 -Random messages. 1-3 line random messages displayed
at/with/in the main menu ANSI.
by =Displays system activity at logon.
+Can forward mail to different networks.
Roland +Do carbon copies to different networks and network addresses.
De Graaf +Sysop always see's actual free space, but can set a setting
to "hide" a certain amount of space--so a user thinks there
($35-$160) is less than there really is.
(3-Feb-92) -Start/end time for netmail only operations.
+Will dial out when a local BBS's TO: message threshold is
reached, otherwise once per day for long distance BBS's.
+Waiting-for-call: can call up historical totals of BBS info.
+Waiting-for-call: can display who's on the other ports.
+"Sysop alert"--beeps you when the user logs off (a when user
on toggle).
-User rec has field for "cost per minute" for LD charges for
using netmail.
-Users can create 9 personal "tag lines" then can include
them into their messages (like macros).
-Can put a format code (eg. !100) so that the text following
that is only shown to level 100+ users in ANSI's.
+Users can request files (via netmail) from a network files
list of another BBS.
-Users may post 5 1-3 line notes to themselves which are
shown at logon.
-Users can do mass mailings to up to 9 lists of nodes.
---Conclusion:
Lots of net support stuff. Docs need improving. Too much
emphasis on a script language.
RemoteAccess +Can disallow DL's during peak hours.
1.11 -Opus or Front Door logging format.
=Supports Windows, DesqView, TopView, MultiLink, DoubleDos
by and PC-MOS/386.
=Interactive EMSI support (IEMSI).
Andrew Milner +Can have up to 9 AKA node addresses for your BBS.
=Messages sizes of up to 20k.
($50 - $?) +SL field for crash attr (Min SL to define a message with
crash).
+SL for file attach.
+Can set a minimum DL baud needed.
=Uses a template to define how directory lists are to look.
+Can define sysop page hours for each day of the week.
+Multi-linqual text.
-Users can select which date format to use/see.
-Toggle to exclude sysop's name from: user list, today's
callers, who's on the other nodes.
=Toggle to only allow IEMSI logons.
=Password checker: disallow passwords in a file, disallow
users first or last name, checks old and new password for
phonetic similarity.
-Can disable inactivity timer by using a zero value.
-Inactivity timer disabled if caller logged in at console.
-After entering an incorrect password (or series thereof) the
system has a toggle for whether to offer the caller a chance
to leave a message to the sysop.
+Can toggle on/off whether the BBS answers the phone (or the
modem).
=Can define message areas as Read Only (useful for
announcements).
=Message file attaches get put into their own unique
directories (mad at the time for UL'ing).
+With AKA net addresses, can assign a different one to
each/different message areas.
-Automatically checks if the protocol selected (having an
"MNP required" toggle) matches up with the user's connection
(user called with an MNP modem).
+Can assign hot keys to display ansi's or exit with error
values.
+"Paging bell" can play a musical file.
-Users can "browse the nodelist" for netmail addresses.
+Users can change their language of choice.
MSYS +Command to close the log file, rename to yymmdd.log and open
Version 1.12 a new one.
by +Command to send a CC of a message out to other BBS's.
Michael +Command to lock the console keyboard, so no keys can be
Pechura entered until a password is entered.
(Free - $30)
(25-Sep-91) ---Conclusion:
Unfortunately this is a packet-radio-first BBS (phone line
support is an aside) making reading and separating out what
is technical for packet-radio and what is unique extremely
difficult. It seems to do everything one could want with
regards to packet-radio.
OPUS =Keeps zone address data in individual data files.
by +Can set a toggle to refuse any incoming net mail.
Wynn Wagner III -Can set an SL for those who can see net mail "extra" lines
(kludge, SEEN-BY, etc.).
(Free)
(7-Jan-87) ---Conclusion:
A basic file/message BBS system.
X-ZotIks 3.8 This is a modified Telegard 2.5. Nothing that Telegard 2.7
by Brian Smith doesn't have. Good example of the futility of modifying
(Free) someone else's BBS code.
FORCE! BBS =Can require a password to access a message area.
Version 3.88 =When editing a user, can enter a SL and it brings up first
by Guy Smith matching SL user (can edit this one or move on to the next).
& Jim Langley
($104) ---Conclusion:
(16-Oct-90) A beginner's BBS. Same basic pieces as any other BBS. Hopes
to do many things, but ends up doing none well.
PICS =When reading mail, command to turn pausing/screen clearing
Version 1.5 off for the rest of the messages (continuous read on).
by =Read messages command to "hide" a message--marks it
Les Archambault restricted so it's invisible to all but the sysop.
(Free) =Can define a start and stop hour to grant extra time.
(7-Mar-87)
---Conclusion:
A primitive BBS. From the very early days.
ROS v2.5 ---Conclusion:
by Steve Fox Very basic and primitive BBS. But there's a newer one out
(Free) I'll get.
(10-Jan-85)
Common Ground =Menu command line allows: "read after 1/1/85 re 'acid raid'"
by to read messages after 1/1/85 that contain 'acid rain' in
Chris Hancock their title.
(Free)
(20-Mar-86) ---Conclusion:
A pretty primitive BBS. Seems to have been designed as a
tutorial.
COLLIE 1.0 +Can toggle off the BBS making long distance calls when doing
by netmail.
Dan P. Plunkett +Keeps track of number of minutes since last reset, number of
minutes system was used, and yields system usage efficiency
($50) in percentage.
(4-Jul-86) +Keeps tallies on how many users called at the various baud
rates.
=When-caller-on hot-key to pop up the system total-stats
screen.
---Conclusion:
An old BBS program. Had netmail, but not much else.
Minotaur 2.0c ---Conclusion:
Douglas Salas Another primitive BBS from the old days.
& William Adams
($30)(9-May-86)
Major BBS +"WFC" screens show the status of each node.
Release 2.2 +"WFC" command to send a message to any or all users.
by Tim Stryker -Internal multitasking for operations.
($n/a) -Requires specialized hardware.
(1-Oct-87) =An advertisements database:
=Automatically deletes the ad's after 1 week.
=Each ad can have up to 50 responses.
=Responses are one line.
=Users may only have one response per ad active at a time.
=Can scan by topic (a subject line).
=4x80 character ad body.
+Can broadcast to all or a specific node.
+Can page a node.
+Can toggle paging of your node.
+Besides accounting per minute of access, it can also charge
for each message posted.
-Keeps track of the profanity level of a users input.
---Conclusion:
The company specializes in the hardware for chat lines. This
software utilizes that hardware, and is generally quite
limited in it's capabilities.
Falken +"WFC" command to list the upcoming events.
Version 6.1 +"WFC" command to watch a node's session.
+"WFC" command to log to file a node's I/O.
by Herb Rose -Internal multi-user system that even allows door programs at
each node.
($120 - $402) +"WFC" command to watch and type-for a node's session.
(27-Oct-91) =Command to give a report on how much email each user has on
the system.
+A "bio's" database: users can enter info about themselves
that others can see.
+Can network together conferences from different BBS's in
real time.
+Teleconferencing commands:
+List active conferences, subjects, and members.
+Make a conference.
+Join/leave a conference.
+Public/private declaring of conference.
+Sysop can make the conference permanent (or not).
+Sysop can force a user out of a conference.
+Buffering of messages (to create long messages) and then
send the buffer.
+Invite a user into your conference.
+Change conference name.
+Put a one line, 70 character, message into a 20 line
conference "chalkboard".
+Commands to view chalkboard and erase chalkboard.
---Conclusion:
Surprisingly, it's quite primitive. It's strengths are it's
multi-line conferences system.
Osiris SE -Warning at logon if an event is coming and that their time
Rev 4.00 was reduced.
-Summary of the time usage info (used and remaining) when
by logoff.
+Search text in a range of messages.
International =When selecting a message base, asks "Which Board <L=list>?".
Tele- +Copy entire message bases or file areas to another area.
Communications -Lots of .EXE files to do tasks (vs a couple big ones).
=Subprogram to do a "purchase system" of items on-line.
($120 - $5000) -Doesn't update high-message-read pointers when pack and DL
(16-Apr-92) messages.
+Echomail watch dog program:
+Imports, processes, exports echomail.
+Automatically removes duplicate messages.
+Keeps track of time used for each action (logs).
+Handles Opus doors
=Menu option to "jump" users to message areas containing new
mail they haven't seen.
+Menu option to give version also says whether operating
under a multi-tasking environment.
+User can display a text file in the files areas.
-For high volume time periods: don't allow dual back to back
calling.
+"Sysop's editorial" menu selection.
+Fidonet support:
+Crash mail support.
+File attached support.
+INFA mail support.
+CRASH/HOLD/NORMAL File attach message.
=arcmail support.
+Gives average number of netmail messages imported per
second.
-Ignores netmail not addressed to the BBS.
="SEEN-BY:" message option.
+Reports on the number of un-sent message bundles.
-Lynxnet support.
+List most/least active message areas.
+List areas within an activity range.
+List areas by % of message traffic through them (messages
added per day).
-"Waiting for caller" screen shows total calls (today or
forever?) and the number of active messages.
-User sends 10 ^G's (bells) to tell sysop to exit chat.
+Individual bulletins for different user level's or to single
users--can be "view once" files ("Bomb Run's").
+Gives % of time BBS in use (x used, out of y, (n%)).
+Total and average and graphs of the info.
+Gives total files tranfers in x connects.
+Total and average and graphs of the info.
+Total UL's and DL's to date.
=Top 10 UL's and what protocol and how much time they used
w/each protocol.
-Compresses ANSI's buy substituting a character for the
graphics combinations.
=Differentiate physical and logical file areas (keep all
files in one area or more, but show lots of areas as
existing) (saves drive space and makes some operations
easier).
+Multinode chat:
-Only lets 1 user type at a time.
=User notes he's done typing by hitting enter at a blank
line (system keys on this).
-Limits on how much a person can type before being forced to
relinquish it to another chatter.
=With hot keys: any key cancels listing, and the key typed is
then attempted to be processed by the menu being returned
to.
+Chat commands:
=Clear "your" window in 2-way chat.
=Clear the screen.
+Dump the screen to a file (console only).
+Show version command also show's DOS version and multi-
tasker and network software, total memory, and the amount
left.
=Users can toggle off the showing of their names in the user
list (shows "private listing" instead for their name).
=Will check the "correctness" of incoming fidomail (to/from
has at least 1 alpha char, numbers ok, etc).
+Can keep track of number of bytes sent to each echomail node
(if wish to do shared billing).
+Can read messages without logging in.
+Sysop can send a message to all names in a standard text
list of names (like @fnames.ctl works).
+Command to create this file (like CC's sort of).
+Can send a range of messages to a text file.
-Asks user before upload if they want to post a message about
the upload.
-After uploading, it automatically posts a message to the
uploader thanking them for the upload(s) (and lists all the
upload(s) in the message).
-Keeps track (for user to see) of their last download CPS
rate.
+Can restrict users to use only certain nodes (eg. to keep
2400 baud users off a 9600 baud line and on a 2400 baud
line).
=Toggle to stop caller calling twice in a row (to require
someone else on between the calls) or after x idle minutes,
or if they have a high enough SL.
---Conclusion:
Great name: God of the lower world and judge of the dead.
Pretty solidly designed. A lot of thought, work, and testing
went into this software. File transfers are a weakness.
Seems too heavily tilted toward the sysop (vs. the users).
Maximus-CBCS =Supports OS/2.
Version 2.00 =Can forward a message to multiple users.
-Uses words for SL's rather than numbers.
by +Users can "expire subscriptions" based on date, or minutes
(used).
Scott J. Dudley +Can have the event play a tune/beep when it's activated.
=Instead of "message base attributes" it uses "security level
message base attributes"--ie, can set up each SL for each
(Free - $900) message bases attributes (no anon for level 5, non for 10,
(4-Nov-91) 20, etc.)
=When entering net address commands: # to list all nodes in
current net, / to list all nodes.
=When reading messages command to display the original message
if the one they are reading is a reply. To display the root
message.
=When reading messages command to display the replies to the
current message being read.
---Conclusion:
A complete and modern BBS program.
SuperBBS 1.15 +Can set net mail to match zones (if message is to zone 2,
by and you have a zone 2 AKA, then use the AKA address as
Risto Virkkala from).
and +File area bits for Age requirement (a field) and whether or
Aki Antman not to do virus checking.
($50) +Can require a minimum age to logon.
(15-Jan-92) +Format commands to define what is to be shown in the who's-
on sysop status line.
=Can set up different menus/paths for different languages
(thus Spanish ANSI's and U.S. ANSI's).
Renegade Version 8-10 Beta by Cott Lang (Free)(10-Aug-92)
Sapphire 4.00L =<<name1><name2>> when put on a message line will make the
rest of the message private except for these users in <<>>.
by You can mix it into messages, to have many private messages
in one: <<john>>
Tim Campbell Hello
<<paul>>
($45) Hi
John will only see "hello", paul will only se "hi".
(30-Jan-92) =As above, except exclusionary fields: ><name1><name2><
=Where there is no text between <<name1>> and <<name2>> (on
two lines) then the two are considered to be one long entry
(rather than relying on long word wraps).
=Can do the above in file descriptions to exclude/include
only specific users (to see/DL).
=Reading messages: 1-9 slow-fast speed change during message
body reading.
+An "announce mode" in which nobody is allowed to log in (BBS
just gives announcements when people call).
=1-9 slow-fast for ascii send of files (sysop's send file
hot-key).
-Who's on status line shows last line entered in the callers
log.
+Hot-key to jump the user immediately into chat screen if
they do a "call for chat"--speeds up process if you're
jumping in and out of chat (if you've accepted to chat once,
then the next time the user in the session selects to chat,
just automatically jump them into it).
+Hot-key to enter a list of names of users allowed on next
(for when looking for a specific person to call back)(list
stays good until sysop clears it or you shut down the BBS).
+As above (list) but to beep when that user(s) call.
+Hot-key to toggle sound on/off (useful in office). Status
line shows ascii music character when sound is on.
=Status line shows status of all the sysop toggles.
---Conclusion:
A basic, simple (simplistic), BBS program, but with its own
philosophy, which is nice to see.
Mach-10 2.4 =Give top ten users (top UL'er, top posters, top callers) the
max extra time to give (for users in all 3 top lists).
by -Call back verify does 3 attempts.
+Command to list all unvalidated users.
Scott M. Baker +Loop through and edit records of all unvalidated users.
+Command to list all locked-out users.
and +Lists top 10 callers based on time on-line.
+Lists top 10 door users--based on time in doors.
Jonathan L. +Break down users and produce % breakdown by age of user.
Woods +Displays % of male/female users.
+Breakdown (%) of the days callers by baud rate.
(8-Oct-90) +File system stats: # of UL's/DL's, time spent ULing/DLing, k
UL'd/DL'd.
(Free) =Message download command: erase packed mail file.
---Conclusion:
A basic BBS system with netmail, a bit out of date.
MIST+ 1.3 ---Conclusion:
by Peter and Edlin as a BBS program. Mist is a script language,
Trudy programmed into a poor BBS.
Johnson-Lenz
($56)(2-Jan-92)
The Silver -Includes Clipper source code.
Bullet 2.0 ="Remote shutdown of BBS" command, exits with an error code
by which allows remote sysop to run a program that requires all
Larry Stewart the systems memory.
and +Keeps track of the number of calls at each baud rate.
John Halovanic +Keeps track of the number of ULs/DLs per node.
($75) =Screen saver is initiated after x minutes.
(19-Oct-89) +User record field for "Maximum download bytes allowed" (for
subscription systems).
---Conclusion:
Not a very powerful BBS, very limited, but does include
source code.
Celerity 1.38 +Can select which set of menu's (and thus BBS's "feel") from
by a list.
Brendon +Can output whole users file to printer.
Woirhaye +Command to locate all new users awaiting validation.
and +New users can be forced to upload, for examination by sysop
Dave Hicks and those voting on the user.
($50) +Users can get credit for when others DL their files.
(17-Feb-92) +Can give 0 points of UL credit at UL, and only rely on when
users DL the file.
+Network spanning databases (such as BBS phone numbers, or
quotes, etc.) When changed on one, updated on all.
+Voting on new users: more like a database: can look at all
awaiting, vote many times, and change their votes, and can
enter a 50 character comment.
=Individual UL/DL ratios (stored in users record)(vs. level-
based ratios).
+Can do "file point loans"--loan limit and min SL defined by
sysop.
+Commissions: UL'er gets a % of the file pts each time file is
DL'd.
=WFC: shows a % of free drive space left. Also uses a bar
graph for the same purpose.
+Can lock-out non-local (area code) users, allow a percentage
of the user base to be them, or vice-versa (lock out a
percentage of locals).
+Can allow only a % of total users to be "slow" (2400 baud)
callers.
+Quick "anyone can download" mode (apple cat systems).
+Freezes time when user and sysop are chatting.
+Beeps once each minute until sysop answers chat or user logs
off.
+Shuttle logon: emergency chat (requires a password--either
its own or the shuttle password).
+Sysop can choose to login invisibly (not show up as last
caller or in log).
+File area contents listings can be set to not show
extensions.
=Asks user: "file is disk x of y" when uploading.
+Can list the file area contents by name, date, popularity,
or random order.
+Ask user for phone number if don't already have it.
+Log analysis: total calls to bbs (and breaks down by baud
rate).
HERITAGE NOTES A "∙∙∙>" means the program was significantly spawned from the
first BBS program. I do not think any were spawned with the
original author's approval, and recommend they be ostracized.
Legality doesn't matter, it's a right or wrong issue.
A "<═══" means it was a valid evolution of the product.
The dates below are for versions that I have last examined.
Not necessarily the latest version available today.
'93
.'92
..'91
...'90
....'89
.....'88
......'87
.......'86
........'85
..Auntie
.......Collie <═══ Colossus (10-Feb-86)
.......Common Ground
..Falken
...FeatherNet
...Force!
....Forum-PC ┬∙∙∙> ViSiON (18-Apr-91)
└∙∙∙> Celerity (17-Feb-92)
...IronHenge <═══ Stonehenge (25-Nov-86)
.Osiris <═══ Lynx II (1-Aug-89)
...Mach-10
......Major
..Maximus
......Minihost
.......Minotaur
.Mist
..MSYS
..OmegaBBS
......Opus
......PICS
....Professional OLEcom
...QuickBBS ┬∙∙∙> RemoteAccess (27-Jan-92)
└∙∙∙> SuperBBS (15-Jan-92)
...RBBS-PC
........ROS
.....RyBBS
..Searchlight
.Sapphire
.????Socrates
..Spitfire
....T.A.G
....The Silver Bullet
........TurboBBS
..UltraBBS
.Virtual
..Wildcat!
..WWIV ┬∙∙∙> Telegard (15-Dec-91) ┬∙∙∙> Radioactive Telegard (15-Oct-91)
│ ├∙∙∙> X-ZotIks (13-Apr-92)
│ └∙∙∙> Renegade (10-Aug-92)
└∙∙∙> ICP (2-Mar-91)
HISTORY These are various historical bits. The BBS program in
parenthesis was the source of the text.
(Stonehenge) Since 1978, when Ward Christensen and Randy Suess developed
CBBS, many bulletin board systems have been developed for
nearly all microcomputers.
(ROS) The original SJBBS, written in Xitan Basic by Howard Moulton,
was adapted to MBasic by Bruce R. Ratoff. Modifications
to this system were made by Bruce Ratoff, James Underwood,
Ron Fowler, Brett Berg, and many, many others. James
Whorton and Eddie H. Curlin converted the RBBS to Turbo
Pascal (copyright Borland International) in 1984 and called
the system TPBBS.
(PICS) ROS version 1.0 (originally released as TBBS23 but changed to
ROS to avoid confusion with TPBBS with which it shares no
code or structure) was written using ideas gathered from
these systems and from others operating on a wide variety of
computers. Version 2.0 of ROS was revised to include indexed
file support using B+ trees provided by Turbo Toolbox
(copyright Borland International). Version 3.0 eliminated
the need for support from programs such as BYE, XMODEM, and
SD by incorporating these functions internally. Steve Fox of
Albuquerque (505-299-5974) is the author of all of the ROS
releases. The file structure of PICS is slightly different
from that of ROS. The low-level routines ROS.MDM and ROS.MCH
are the ones PICS uses.
(Stonehenge) The basic structure is based on the "room system" concept
originally developed by Cynbe ru Taren and Glenn Gorman with
Citadel and Minibin. The program uses a "standard" Citadel
user interface with an extension of the Citadel command set
to use the additional functions that the STONEHENGE software
offers. while STONEHENGE strongly resembles Citadel from the
outside, the internal code is completely original and has
little in common with the original citadel program other than
a room based structure.
(IronHenge) The computer bulletin board program entitled "Stonehenge" was
created in 1984 as a gift from David Bonn to myself [Kalen
Bonn].
(RA) As an added bonus, we have decided to use the QuickBBS-style
user and message database formats. This means that you can
continue to use your favorite QuickBBS utilities with no
need to convert to another format. Any incompatibilities in
the configuration files is taken care of by an upgrade
utility. We make no apology for the similarity between
RemoteAccess and QuickBBS. QuickBBS had many features that
we wanted, and compatibility gives the added bonus of
offering the sysop ease of installation and a familiar
environment. [They also used the same menu system.]
from tbbs8502:
Documentation for version 8501, 8502 of the Experimental TurboBBS.
This documentation is for the changes that have been made to version 1.05
of Robert Maxwell's TurboBBS.
I wish to publicly thank R. H. Maxwell for such a fine BBS to start with!!!
In all my years of coding I have rarely run across a program which is
structured so nicely (even in Pascal). The code makes it a breeze to add new
features to.
[ck out the last/latest version of tbbs, need to decide on version numbers,
and whether "Experimental TurboBBS" is the new name for TurboBBS (an
evolution) or whether there's a newer "TurboBBS", etc.]
There are 3 major components to a BBS program:
1. Message system
2. File system
3. Menu system
The following are not components of a BBS:
1. Communications program (use Boyan, etc.)
2. Database program (use DBase, etc.)
3. ANSI screens (create via TheDraw, etc.)
4. File transfer protocols (use DSZ, etc.)
5. Communictions routines (use X00, etc.)
6. Operating systems (use DOS, etc.)
7. Script langauges (use Basic, etc.)
8. Net mail (use FrontDoor, etc.)
A BBS is not a sum of various parts, but a whole.
The U.S. Supreme court has a small (like 8 nodes) net for distribution of
their decisions. This net is known as Hermes (which means "messager of the
gods").
If any of you have more historical information. Do tell me.